Add automated glossary linking with complete term coverage#88
Add automated glossary linking with complete term coverage#88solzlivinglife wants to merge 6 commits intorobotframework:mainfrom
Conversation
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-88.surge.sh/robotframework-RFCP-syllabus/ |
|
|
||
| :::: | ||
|
|
||
| All arguments that are defined after a :term[Variable Number of Positional Arguments] (`*varargs`) are :term[Named-Only Arguments]{term="Named-Only Argument"}. |
There was a problem hiding this comment.
Here in this line is the correct way how a link should be build up. So not a regular Markdown link, but :term[singular or plural seen in the doc]{term="syllabus term"}
That would then look like: 
Implement GlossaryTerm React component per reviewer feedback
- Created GlossaryTerm.tsx component with hover tooltips - Added GlossaryTerm.module.css for styling with dotted underlines - Updated glossary linker to output component format instead of markdown links - Uses placeholder system to prevent nested components - Excludes :term[] directives, code blocks, headings, and existing links - Skips learning_objectives.md (reference table) - Auto-adds import statements to modified files - Supports plural/singular matching and case-insensitive linking - ~412 glossary links across 31 files
solzlivinglife
force-pushed
the
glossary-links-fixed
branch
from
cbec970 to
2a4cb0d
Compare
|
🚀 Preview deployed to https://robotframework-RFCP-syllabus-pr-88.surge.sh/robotframework-RFCP-syllabus/ |
|
There should not happen any renumbering of Learning Objectives and please do not use the glossary technique in Learning Objectives. |
|
In the glossary it not says everywhere However, that should be: This is part of a docusaurus plugin, which makes for the right formatting |
3 participants
Features: